사이트 내 전체검색
Persistent “disk will be checked…” in the message of the day (motd) even after reboot
로빈아빠
https://cmd.kr/server/683 URL이 복사되었습니다.

본문

 

I see that there are some other threads that mention this error, but I have tried the solutions with no luck.

When I log into my 12.04 Server, I get the message:

/dev/sdb1 will be checked for errors at next reboot
/dev/sdc1 will be checked for errors at next reboot

The problem is that the check is never done and I continue to get the messages. I ran a fsck on both drives and they are fine.

share improve this question
   
I just rebooted again and didn't get the warning... –  dpbklyn Jul 13 '12 at 14:46
   
I tried a suggestion to do touch /forcefsck and reboot, but I'm still getting this warning. –  pcm Sep 5 '12 at 20:40 
   
   
The message in the message of the day (motd) about drives being checked doesn't go away even when the drives have been checked. This is a known bug in Ubuntu. This is caused because that message is cached in the file /var/lib/update-notifier/fsck-at-reboot so that it is not constantly recomputed. /usr/lib/update-notifier/update-motd-fsck-at-reboot checks the timestamp on the file and is supposed to regenerate it every so often. However, there is a bug and the timestamp gets set in such a way that it never regenerate –  Stephen Ostermiller Apr 20 '13 at 10:12 

This is a known bug in Ubuntu 11.04 and apparently still exists in 12.04 LTS. What happens is what you described: you keep getting the notification even though there is nothing wrong with your hard drive and no checks are scheduled/will be done.

It's caused by the /usr/lib/update-notifier/update-motd-fsck-at-reboot script generating a /var/lib/update-notifier/fsck-at-reboot file with a timestamp in the future. The previous link has a convoluted solution from one of the Ubuntu maintainers (Steve Langasek), but it may be simplestto just do this:

  1. Open a terminal with Ctrl-Alt-T
  2. Type:

    sudo rm /var/lib/update-notifier/fsck-at-reboot
    
  3. Exit the terminal and reboot (or logout/login).
share improve this answer
   
In my case editing the file and removing the text resolved the problem. When I tried removed it at next login it would simply recreate the file so it the problem would persist. –  Savas Vedova Feb 14 at 10:54
   
Here a command that will fix the problem without any sort of reboot or logout: sudo bash -c 'rm /var/lib/update-notifier/fsck-at-reboot && for file in /etc/update-motd.d/*; do $file; done > /var/run/motd' && cat /etc/motd –  Stephen Ostermiller May 9 at 19:24
i.gif?e=eyJhdiI6NDE0LCJhdCI6NCwiY20iOjk1NTYwLCJjaCI6MTY1MzEsImNyIjoyNjY1NjMsImRpIjoiN2UyMDhmM2ViY2IxNDRmY2E4ZTI2YTU5ZDYzMTdmZmQiLCJkbSI6MSwiZmMiOjMzMDkyMCwiZmwiOjE3MTc0MSwiaXAiOiIxMjIuMzYuOTIuNzQiLCJrdyI6ImhhcmQtZHJpdmUsZnNjayxtb3RkLHgtY29tbXVuaXR5LHgtaG9zdC1hc2t1YnVudHUuY29tIiwibnciOjIyLCJwYyI6MCwicHIiOjU3MjIyLCJydCI6MSwicmYiOiJodHRwczovL3d3dy5nb29nbGUuY28ua3IvIiwic3QiOjU2NzQ5LCJ1ayI6InVlMS00ZTE5NGE0ZThkOTQ0NjlmYjM3Y2MyMzljNmJmMTQ2YyIsInpuIjozMCwidHMiOjE0MDcyOTI4ODM0NzJ9&s=VbJF32apDC2Uti6IVOAF0fNu4EA

댓글목록

등록된 댓글이 없습니다.

1,139 (3/23P)

Search

Copyright © Cmd 명령어 18.119.157.39